N4 supports EDIFACT standard IFTMBC message, release D & version 98B.
UI Navigation: Administration > EDI > Message Types
This specification provides the Booking confirmation message (IFTMBC) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and forwarding/transporting parties. In a terminal, IFTMBC Edi is received from Forwarding/Transport parties.
This message:
Permits the transfer of data from a Forwarding/Transporting parties
It can be used whenever a confirmation of the booking of a consignment is deemed necessary as an answer to a booking provisional or booking firm message concerning a certain consignment.
It can also be used to confirm cargo particulars and equipment requirements.
A confirmation might read that the booking of a consignment is accepted, pending, conditionally accepted or rejected.
The following sections of this document explain how the IFTMBC message is handled in N4 and scope of its implementation.
IFTMBC D 98B Inbound Supported Segments
Following table illustrates the segments of EDIFACT standard IFTMBC D 98B message & scope of each segment in N4.
|
S.No |
Group |
Segment ID |
Supported Qualifier |
Description |
Supported in N4? |
|---|---|---|---|---|---|
|
1 |
|
UNH |
|
Message Header |
Supported |
|
2 |
|
BGM |
|
Beginning of message |
Supported |
|
3 |
|
CTA |
|
Contact Information |
Not Supported |
|
4 |
|
COM |
|
Communication Contact |
Not Supported |
|
5 |
|
DTM |
2, 63, 137 |
Date/Time/Period |
Supported |
|
6 |
|
TSR |
|
Transport Service Requirements |
Not Supported |
|
7 |
|
FTX |
AAI, BLR, AAA |
Free text |
Supported |
|
8 |
|
CNT |
|
Control Total |
Not Supported |
|
9 |
SG1 |
LOC |
7, 9 , 11 |
Details of transport |
Supported |
|
10 |
|
DTM |
|
Date/Time/Period |
Not Supported |
|
11 |
SG2 |
RFF |
BN, ERN |
Reference |
Supported |
|
12 |
|
DTM |
|
Date/Time/Period |
Not Supported |
|
13 |
|
TCC |
|
Transport Charge/Rate Calculations |
Not Supported |
|
14 |
SG3 |
TDT |
|
Details of Carriage Level Info |
Supported |
|
15 |
|
DTM |
|
Date/Time/Period |
Not Supported |
|
16 |
|
TSR |
|
Transport Service Requirements |
Not Supported |
|
17 |
SG4 |
LOC |
7, 9 , 11 |
Details of transport |
Supported |
|
18 |
|
DTM |
|
Date/Time/Period |
Not Supported |
|
19 |
SG5 |
RFF |
|
Reference |
Not Supported |
|
20 |
|
DTM |
|
Date/Time/Period |
Not Supported |
|
21 |
SG6 |
NAD |
CA, CN, OS, CZ, SF |
Name And Address |
Supported |
|
22 |
|
LOC |
|
Details of transport |
Not Supported |
|
23 |
SG7 |
CTA |
|
Contact Information |
Not Supported |
|
24 |
|
COM |
|
Communication Contact |
Not Supported |
|
25 |
SG8 |
TSR |
|
Transport Service Requirements |
Not Supported |
|
26 |
|
RFF |
|
Reference |
Not Supported |
|
27 |
|
LOC |
|
Details of transport |
Not Supported |
|
28 |
|
TPL |
|
Transport Placement |
Not Supported |
|
29 |
|
FTX |
|
Free Text |
Not Supported |
|
30 |
SG9 |
GID |
|
Information about the Packaging of Goods |
Not Supported |
|
31 |
|
HAN |
|
Handling Instructions |
Not Supported |
|
32 |
|
TMP |
|
Temperature |
Not Supported |
|
33 |
|
RNG |
|
Range |
Not Supported |
|
34 |
|
TMD |
|
Transport Movement Details |
Not Supported |
|
35 |
|
LOC |
|
Details of Transport |
Not Supported |
|
36 |
|
FTX |
|
Free Text |
Not Supported |
|
37 |
|
PCD |
|
Percentage Details |
Not Supported |
|
38 |
SG10 |
NAD |
|
Name And Address |
Not Supported |
|
39 |
|
DTM |
|
Date/Time/Period |
Not Supported |
|
40 |
|
GDS |
|
Nature Of Cargo |
Supported |
|
41 |
SG11 |
MEA |
|
Measurements |
Not Supported |
|
42 |
|
EQN |
|
Number Of Units |
Not Supported |
|
43 |
SG12 |
DIM |
5, 6, 7, 8, 9 |
Dimension |
Supported |
|
44 |
|
EQN |
|
Number Of Units |
Not Supported |
|
45 |
SG13 |
RFF |
|
Reference |
Not Supported |
|
46 |
|
DTM |
|
Date/Time/Period |
Not Supported |
|
47 |
SG14 |
DOC |
|
Document/Message Details |
Not Supported |
|
48 |
|
DTM |
|
Date/Time/Period |
Not Supported |
|
49 |
SG15 |
DGS |
|
Dangerous Goods |
Supported |
|
50 |
|
FTX |
AAD |
Free Text |
Supported |
|
51 |
SG16 |
CTA |
|
Contact Information |
Not Supported |
|
52 |
|
COM |
|
Communication Contact |
Not Supported |
|
53 |
SG17 |
MEA |
|
Measurements |
Supported |
|
54 |
|
EQN |
|
Number Of Units |
Not Supported |
|
55 |
SG 18 |
EQD |
|
Equipment Qualifier |
Supported |
|
56 |
|
EQN |
|
Number Of Units |
Supported |
|
57 |
|
TMD |
|
Transport Movement Details |
Not Supported |
|
58 |
|
MEA |
|
Measurements |
Not Supported |
|
59 |
|
DIM |
|
Dimension |
Not Supported |
|
60 |
|
HAN |
|
Handling Instructions |
Not Supported |
|
61 |
|
TMP |
|
Temperature |
Not Supported |
|
62 |
|
FTX |
|
Free Text |
Not Supported |
|
63 |
|
RFF |
|
Reference |
Not Supported |
|
64 |
SG19 |
NAD |
|
Name And Address |
Not Supported |
|
65 |
|
DTM |
|
Date/Time/Period |
Not Supported |
|
66 |
|
UNT |
|
Message Trailer |
Not Supported |
IFTMBC D 98B Inbound - Message Functions
As per EDIFACT standard, IFTMBC has various message function codes in BGM segment and N4 supports the following message functions are supported
BGM+661+WCP00000530901+9+AB' – Here "9" is the message function qualifier.
|
Qualifier in the EDI message |
Value in the XML |
|---|---|
|
9 |
O - Original |
|
2 |
A - Add |
|
3 |
E - Delete |
|
4 or 33 |
U - Change |
|
1 |
D - Cancel |
|
5 |
X - Replace |
For information on the EDI message functions supported by IFTMBC, see Supported EDI message functions (on page 1).
IFTMBC D 98B Inbound N4 Built-in Map
N4 serves a built-in map which is used to convert IFTMBC Edi message into Navis standard booking xml. This xml in turn used for further processing.
Following are the related files, part of N4 application and can be downloaded:
iftmbc_D_98B.mgt- GoXml map
iftmbc.dic -Edifact standard dictionary
booking.xsd - Navis standard xml schema
UI Navigation: Administration > EDI > Message Types
Special Cases
edi:BookingItem mapping
Added a filter (/EDI/Group_Loop/IFTMBC/SG18/EQD/C237@A_8260==NULL) such that this tag will be displayed only when the EQD segment has no equipment number.
Added a match to SG18 loop (EQD Loop).
edi:BookingEquipment and edi:ediContainer mapping
Added a filter (/EDI/Group_Loop/IFTMBC/SG18/E
N4 has a way of validating some business conditions which might be applicable for some clients and not for some. So those validations are made configurable, the user may turn it on if the particular validation is needed or turn it off if not needed.
The following table lists such configurable settings applicable for IFTMBC message:
|
Name |
Description |
Edit UI |
Usage |
|---|---|---|---|
|
ARGOBOOKING001 |
Import To Transship |
Session |
To change import containers to transship containers. |
|
ARGOBOOKING002 |
Allow container Update |
Settings |
Create new pre-advised export containers. Update existing containers to associate them to the export booking. |
|
ARGOBOOKING003 |
Allow creation of Foreign Vessel Visits |
Session |
To create a vessel if the vessel specified in a BOOKING EDI message is not in N4. |
UNB+UNOA:2+RIK+RIK+081222:0310+45978'
UNH+25507360+IFTMBC:98B:UN'
BGM+772:::BOOKING CONFIRMATION+25507001+9'
DTM+137:200807010308:203'
TSR+3'
FTX+AAI+++FURNITURE'
RFF+VON:726'
TDT+20+001+1+RIK:172:20++726:103::RIK VESSEL'
LOC+9+NZLYT:139:6:NORTHPORT,P.KLANG+CT1:TER:ZZZ'
LOC+11+SGSIN:139:6'
LOC+8+HKHKG:139:6'
LOC+7+NZLYT:139:6'
DTM+132:200807252100:203'
DTM+133:200800010800:203'
NAD+CF+RIK:160:166'
GID+1'
EQD+CN+45G0:102:5+2+5'
EQN+1'
TMD+3'
MEA+AAE+G+KGM:23020'
RFF+HS:940300'
NAD+CZ+A046:160:166++HAPAG-LLOYD' UNT+22+22507360'